Actual behavior

The use of std::shared_ptr was unfortunate. I initially had trouble with std::unique_ptr:

• it is impossible to iterate over an std::initializer_list<std::unique_ptr<T>> as it always make a copy
• the constructor of std::vector<std::unique_ptr<T>> make use of std::initializer_list

Desired behavior

The data should be owned by the modules, and std::shared_ptr does not indicate that.

Changes

FSM:

• ♻️ 💥 Use std::unique_ptr instead of std::shared_ptr
• ✨ Add state_trait concept
• ♻️ 💥 The simple_machine::set_state() transition now accepts a value that satisfies state_trait, it will be copied in an internal std::unique_ptr
• ✨ Add a simple_machine::clear_state() transition
• ♻️ 💥 The stack_machine::push_state() transition now accepts a value that satisfies state_trait, it will be copied in an internal std::unique_ptr

Behavior Tree:

• ♻️ 💥 Use std::unique_ptr instead of std::shared_ptr
• ✨ Add node_trait concept
• 🔥 💥 Remove all make() static methods
• ♻️ 💥 Replace std::initializer_list with std::vector
• ✨ Add node_list() template function helper to create the std::vector using a parameter pack

Utility AI:

• ♻️ 💥 Use std::unique_ptr instead of std::shared_ptr
• ✨ Add action_trait concept
• ♻️ 💥 Replace std::initializer_list with std::vector
• ✨ Add action_list() template function helper to create the std::vector using a parameter pack

GOAP:

• ♻️ 💥 Use std::unique_ptr instead of std::shared_ptr
• ✨ Add action_trait concept
• ♻️ 💥 Replace std::initializer_list with std::vector
• ✨ Add action_list() template function helper to create the std::vector using a parameter pack
• ♻️ The plan now takes ownership of the action list given to the planner, the queue is a queue of indices into the action list, this allows to forge a reference to a std::unique_ptr (since an action can appear multiple times in a plan)